Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1576

reference: 359-tree-1
name: 1576
tree-preservation-order: undefined
359-tpo-1
uprn
address-text
point: POINT (-1.046924 50.892903)
geometry: MULTIPOLYGON (((-1.046824 50.892892,-1.046829 50.892912,-1.046842 50.892930,-1.046864 50.892944,-1.046892 50.892953,-1.046922 50.892956,-1.046953 50.892953,-1.046981 50.892945,-1.047003 50.892931,-1.047018 50.892913,-1.047023 50.892894,-1.047019 50.892874,-1.047005 50.892857,-1.046983 50.892843,-1.046956 50.892834,-1.046925 50.892830,-1.046894 50.892833,-1.046866 50.892842,-1.046844 50.892856,-1.046829 50.892873,-1.046824 50.892892)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL